Create a migration session for storage groups with SRDF/Metro protection

Unisphere for PowerMax supports the migration of storage groups that are protected by SRDF/Metro.

Prerequisites

See Roles and associated permissions to determine the user roles that can perform this task.

The data migration environment exists between three candidate storage systems, Metro Array 1 (source), Metro Array 2 (partner array), and the New Metro Array (target). The New Metro Array requires PowerMax OS 10.1.0.0 or later, Metro Array 1 (source) and Metro Array 2 requires Hickory SR or later.

If the SRDF/Metro protected storage group has DR, the DR is on one side only.

The selected storage group is not participating in an SRDF/MetroDR Environment.

The selected storage group is a masked candidate storage group.

The selected storage group does not contain only gatekeepers.

The local storage system must have online SRDF ports.

About this task

The precopy option allows storage to be provisioned on the target storage system without making the host of the devices visible. This option allows the application to continue running on the source storage system while data is being copied to the target.

Minimally disruptive migration allows migrations on the same supported platforms as NDM but it requires a short application outage.

See Understanding migration for additional information.

To create a migration session:

Steps

Select a storage system.
Select Storage > Storage Groups.
Select a storage group with SRDF/Metro protection.
Click and click Migrate.
Select the target storage system.
Click Next.
Select the target Storage Resource Pool (SRP).
Optional: Clear the Enable Data Reduction check box to turn off data reduction.
Data reduction is only allowed on All Flash systems running the HYPERMAX OS 5977 Q3 2016 Service Release or higher.
Optional: Click Precopy.
The SRDF Group selection options are:
- Automatic- selected as default.
- Manual- when selected the Select button is displayed.
  1. Click Select, the SRDF Group window is displayed.
  2. Select an SRDF Group from the list (provided by Metro Array 2) and click OK.
  3. The Edit button is displayed enabling the user to select a different SRDF Group.
Optional: Select Use Bias to enable Bias.
The Witness mechanism must be set up on the New Metro Array prior to migration. A suitable Witness such as the same vWitness instance s available on both the New Metro Array and Metro Array 2 or a Witness array that is configured from the New Metro Array and Metro Array 2 . If a suitable witness is not available on the New Metro Array, the Use Bias option is disabled.
Click Next.
The Target Masking Options page is displayed. Information on one or more masking views along with their associated ports groups, ports, host, and initiators, is displayed. If WLP is enabled (statistics are available for source storage group and target storage system), a suitability score is also displayed.
Review the target masking options and any associated warnings (see Non-Disruptive Migration (NDM) warning messages and failure cases).
Optional: Click next to the port group to display a dialog allowing you to modify the port group parameters. Click OK when complete.
is displayed for the following scenarios:
- Single masking view
- Multiple masking views where all masking views share the same port group.
- Device overlap where all masking views for all SGs share the same port group and no duplicate paths are created (a duplicate path is the same initiator to port mapping in multiple masking views). When devices overlap multiple SGs with different port groups, the wizard allows you to open the edit dialog. The port group names cannot be changed, different ports can be chosen.
- "Zoning required" cases where the port group does not exist on the target storage system:
  - If WLP is enabled, ports are pre-selected based on utilization.
  - If WLP is not enabled, you can select the ports.
FA (Fibre Channel): Relies heavily on SE port selection rules. If source PG name exists on target storage system, use it. If no PG name match exists, but log in history table entries (active and historical) exist to host initiator WWNs, put all ports in one PG and use those ports. If no zoning exists, WLP selects ports. Suitability is done using active paths for cases 1 and 2. Load is spread across all selected ports in case 3.

FN (Fibre Channel) and SE (GigE) : Not supported.
Optional: Review the updated target masking options and any associated warnings.
Click Next.
On the Summary page, review the details. Optionally click Save Migration Report to save the migration report to a PDF file. This option is only available in cases where zoning is required.
If zoning is required, save the zoning report and press Add to Job List . The Add to Job List is the only option available in this scenario, Run Now is not available.
The purpose of the Zoning Report is to present the remaining zoning that is required to satisfy the NDM zoning requirements. If an initiator in an initiator group has no login history table (LHT) entries to any ports in the port group in a masking view on the target storage system, a zoning report can be generated laying out the requirements to get the migration to succeed. However, if an initiator in an initiator group has logins to some ports in a port group on the target storage system, but not all, no zoning report is offered, because the requirements of the migration have been satisfied.
Do one of the following:
- Click Run Now to perform the operation now.
- Expand Run Now and click Add to Job List to add this task to the job list, from which you can schedule or run the task at your convenience. For more information, see Schedule jobs and Preview jobs.